-
Notifications
You must be signed in to change notification settings - Fork 381
build: migrate from setup.py to pyproject.toml #1458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
for more information, see https://pre-commit.ci
rgaiacs
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks a great start. All the tests are failing, probably because of the new test. Can change in the GitHub actions configuration be change to increase the version of Python to be used?
removes: - MANIFEST.in (handled by setuptools-scm) - setup.py (declarative in pyproject.toml) - versioneer (replaced with setuptools-scm) - setup.cfg (was for versioneer)
# Conflicts: # .github/workflows/release.yml
|
@rgaiacs if you want to have a look, I think this might be ready now |
rgaiacs
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few minor comments. Looks good to me.
|
test (24.04, 3.13, conda) is taking too long to finish and failing. |
|
That test normally takes about 15 minutes, so I think something's definitely wrong, but likely not related to this PR. |
|
latest run succeeded in 12 minutes. We should probably have a per-test limit, though, to avoid this problem costing us 6 hours of CI time |
This improves dependency management, IDE support, and aligns with current Python packaging standards.